← Back to issue list

remote-build always recovers, even when --recover is not specified

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1913599
Type
issue
State
open
Author
~nymea
Labels
Created
2021-01-28 14:24:22.309519+00:00
Updated
2021-02-25 13:26:56.297545+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

To reproduce, start a remote-build, and make the client fail somehow. Wait for the remote build to finish or fail (doesn't matter). Then start another remote-build with a different revision of the source code *without* specifying --recover. => snapcraft will recover the previous build and report the status instead of actually building the new source. Given that snapcraft clean doesn't seem to clean remote builds, this makes it close to impossible to use snapcraft remote-build in some sort of automated build environment as one never knows what the build artifact is actually based on.

Evaluation history

No evaluation history available.